home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19970929-19971216
/
000188_news@newsmaster….columbia.edu _Tue Oct 28 08:38:44 1997.msg
< prev
next >
Wrap
Internet Message Format
|
1997-12-15
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id IAA16317
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 28 Oct 1997 08:38:43 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id IAA00588
for kermit.misc@watsun; Tue, 28 Oct 1997 08:38:43 -0500 (EST)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: minix kermit woes
Date: 28 Oct 1997 13:38:41 GMT
Organization: Columbia University
Lines: 22
Message-ID: <634pt1$b6d$1@apakabar.cc.columbia.edu>
References: <Pine.SUN.3.96.971027223205.22923B-100000@nyx>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:7969
In article <Pine.SUN.3.96.971027223205.22923B-100000@nyx>,
douglas shawhan <dshawhan@nyx.net> wrote:
: I am having a small problem using kermit to access lynx on my shell
: account... the text is garbled and many of the curses-type characters
: appear as asterisks. How can I get kermit to behave like a proper vt100
: terminal? I am using 16 bit minix.
:
And so therefore you are using C-Kermit? The current version of which,
by the way, is 6.0:
http://www.columbia.edu/kermit/ck60.html
If you glance at the documentation, you'll see that C-Kermit does not
perform terminal emulation at all. It is a semitransparent (or, if you make
it so) a fully transparent communications pipe between the remote computer
or service you have used it to connect to and your local terminal, terminal
emulator, terminal window, or console, which provides the terminal
functions. Probably you have an ANSI-like console but your host thinks you
are using a VT100, thus the fractured screens. Solution: let the host know
you have an ANSI terminal (or whatever the type really is).
- Frank